Content publishing for personalized content aggregation platform

ABSTRACT

Network devices provide, to a content source device, an uplink user interface to describe and upload video content. The network devices receive, via the uplink user interface, descriptive information for the video content and generate, based on the descriptive information received via the uplink user interface, a unique content identifier for the video content. The network devices incorporate, based on the descriptive information, a listing of the video content into a catalog of content available to users of a content distribution network. The network devices receive, from the content source device, the video content and receive, from a user device, a request to view the video content that includes the unique content identifier. The network devices provide, to the user device, a link to enable the user device to access the video content via the content distribution network.

BACKGROUND

Along with live linear television content, service providers also offerproducts that allow customers to download video content (e.g., streamingvideo, video files, etc.) on demand over a distribution network.Broadcast content options may be presented to the customer via anelectronic program guide. Access to on-demand video content is typicallypresented to the customer via a catalog of available items. Customersmay supplement consumption of live linear television and/or on-demandcontent with content available through various Internet web sites.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating concepts described herein;

FIG. 2 is an exemplary network in which systems and/or methods describedherein may be implemented;

FIG. 3 is a block diagram of exemplary components of a device that maycorrespond to one of the devices of FIG. 2;

FIG. 4 is a block diagram of exemplary functional components of thenavigation device of FIG. 1;

FIG. 5 is a block diagram of exemplary functional components of thevideo content management system (VCMS) of FIG. 2;

FIG. 6 is a block diagram of exemplary functional components of thecontent delivery system of FIG. 2;

FIG. 7 is a block diagram of exemplary functional components of theapplication server of FIG. 2;

FIG. 8 is a block diagram of exemplary communications among devices in aportion of the network of FIG. 2;

FIG. 9 is an exemplary user interface publishing video content accordingto an implementation described herein; and

FIG. 10 is a flow diagram of an exemplary process for publishing contentfor access via a personalized channel according to an implementationdescribed herein.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements.

Systems and methods described herein may enable users to publish videocontent for distribution over controlled networks. The published contentmay be distributed for direct viewing by subscribers or made availablefor use in a personalized content aggregation platform. The personalizedcontent aggregation platform allows users to configure personalizedcontent schedules (also referred to herein as “personalized channelplans”) from multiple content sources and/or for multiple types ofcontent. In one implementation, the personalized channel plan may beconfigured using a navigation device (e.g., a tablet computer or smartphone), which may instruct a display device (e.g., a set-top box orsmart television) to present the content for the personalized channelplan according to the configured time and sequence. In anotherimplementation, the personalized channel plan may be shared with otherusers (e.g., via social media, instant messages, etc.).

As described further herein, content available for inclusion inpersonalized channels may include (but is not limited to) traditionalbroadcast/cable television content, on-demand content, micro-publishedrecorded video, and micro-published live content. Micro-publishedcontent (e.g., video files and/or live content that typically do not getviewed by a large number of viewers) has typically been restricted todistribution via video-sharing or streaming web sites over public accessnetworks, such as the Internet. As such, providers of micro-publishedcontent (or self-published content) typically cannot guarantee the samequality of experience for their viewers as is typically provided withcontrolled-access networks, such as, for example, a cable televisionsubscription service. Systems and method described herein provide toolsto allow subscribers the similar access and delivery for micro-publishedcontent as is typically provided for traditional broadcast/cablecontent.

FIG. 1 is a diagram illustrating concepts described herein. A navigationdevice 110 (e.g., a tablet computer, smart phone, etc.) may be equippedwith a personal channel manager application that enables a user toselect a personalized channel plan 115 of linear and/or non-linearcontent that can be presented on a viewing device 120 (such as a set-topbox (STB) and/or television). The personalized channel plan 115 mayinclude content from, for example, multiple linear television channels(e.g., different physical or virtual television channels), video ondemand (VOD) content, games, social media sites, video-sharing websites,etc. For example, navigation device 110 may obtain a catalog ofavailable content from a content distribution network 130, which may beoperated by a service provider that provides subscription-based services(e.g., television services, Internet access services, and/or othertelecommunications services).

Content provided through content distribution network 130 may originatewith content sources 140, such as content sources 140-1 and 140-2.Content source 140-1 represents a large-scale content provider, such asa commercial television network. Content source 140-2 represents asmall-scale content provider, such as a micro-publisher. Content sources140-1 and 140-2 may generate content 145-1 and 145-2, respectively, andmay provide content 145-1 and 145-2 to content distribution network 130for delivery to subscribers with access to content distribution network130 (e.g., via navigation device 110 and/or viewing device 120). Content145-1 and 145-2 may be provided to content distribution network 130 viadifferent methods, such as a dedicated network connection, the Internet,or even physical delivery. Content distribution network 130 may processcontent received from content sources 140, catalog the content, andgenerate a dedicated channel/link that can be used to access the contentwith, for example, a guaranteed quality of service. While such contentmanagement has typically been available for large-scale contentproviders, these advantages have not generally been available tomicro-publishers.

To configure a personalized channel, a user of navigation device 110 mayselect any available content (e.g., using an electronic catalog fromcontent distribution network 130 or another program guide) and scheduleavailable time slots. The schedule of programming may include livelinear broadcast content that corresponds to a specific program timeand/or recorded programs, which may be presented via the personalizedchannel on a delayed basis (e.g., at some scheduled time after theoriginally-broadcast program time). The schedule of programming may alsoinclude on-demand content (e.g., VOD content) or non-linear content,such as social media content or games.

Navigation device 110 may identify (or discover) available viewingdevices 120 (such as a set-top box (STB) and/or television) on whichcontent from personalized channels can be presented. For example,navigation device 110 may identify viewing devices 120 via localwireless networks (e.g., WiFi network, Bluetooth network, etc.). In oneimplementation, viewing devices 120 may be equipped with hardware and/orsoftware to enable communication with navigation device 110. Using thepersonal channel manager application, a user may select a particularviewing device 120 on which to present content based on personalizedchannel plan 115.

According an implementation described herein, navigation device 110 mayobtain, from content distribution network 130, links to content inpersonalized channel plan 115. For example, the personal channel managerapplication on navigation device 110 may obtain a separate link for eachcontent item. Each separate link may be obtained either at the time ofscheduling or at a point prior to the scheduled presentation time forthe particular content. In one implementation, the link may provide anetwork location for content formatted particularly for a type ofviewing device 120. As used herein, a “link” may generally refer to anypointer or instruction to identify a location, such as a uniformresource locator (URL), an Internet Protocol (IP) address, or channelindicator.

Navigation device 110 may provide links for content in the personalchannels to viewing device 120 and control the presentation of contenton viewing device 120. For example, navigation device 110 may causeviewing device 120 to access a particular link or “tune” to a particularbroadcast channel at a particular time, according to the schedule ofprogramming in the personalized channel. In one implementation, viewingdevice 120 may retrieve content via a controlled access network, such asa closed cable and/or fiber-optic distribution network, that can provideguaranteed quality of service (QoS) levels.

Thus, navigation device 110 may control viewing device 120 to present apersonalized linear aggregation of programming (e.g., a personalizedchannel) that includes a variety of types of content from a variety ofdifferent sources, including different broadcast channels (e.g.,representing different television networks), micro-published content,and/or different network locations.

FIG. 2 is an exemplary network 200 in which systems and/or methodsdescribed herein may be implemented. As illustrated, network 200 mayinclude content sources 140, a video content management system (VCMS)210, a data center 220, a profile server 230, an advertising server 240,a suggestion engine 250, a customer support system 260, user devices270, a private network 280, an access network 290, and a web server 295.VCMS 210, data center 220, profile server 230, advertising server 240,suggestion engine 250, customer support system 260, and private network280 may be part of content distribution network 130. The particulararrangement and number of components of network 200 shown in FIG. 2 areillustrated for simplicity. In practice there may be more contentsources 140, VCMSs 210, data centers 220, profile servers 230,advertising servers 240, suggestion engines 250, customer supportsystems 260, user devices 270, networks 280/290, and/or web servers 295.Components of network 200 may be connected via wired and/or wirelesslinks.

Content sources 140 may include one or more content source devices toprovide any type or form of content to VCMS 210 for distribution. Forexample, content source 140 may include free television broadcastproviders (e.g., broadcast providers, such as NBC, CBS, ABC, and/or FOX)and for-pay television broadcast providers (e.g., TNT, ESPN, HBO,Cinemax, CNN, etc.) that permit content to be streamed and/ordownloaded. Content sources 140 may also include on-demand contentproviders (e.g., video on demand (VOD) providers, pay per view (PPV)providers, etc.), online content providers (e.g., webcasts, podcasts,etc.), etc. According to implementations described herein, contentsources 140 may also include micro-published content providers, such asvideo content generated from mobile devices, video cameras, and otherconsumer electronics equipment, and that is not typically viewed by alarge number of viewers.

VCMS 210 may include one or more network devices, or other types ofcomputation or communication devices, to aggregate content and contentmetadata, process content, and distribute content. In oneimplementation, VCMS 210 may include a content delivery system 212 and adigital rights management (DRM) server 214. VCMS 210 may aggregatecontent and transcode content into a digital format suitable forconsumption on particular user devices 270. For example, VCMS 210 mayinclude a transcoding device to convert a video file from one format toanother (e.g., from one bit rate to another bit rate, from oneresolution to another, from one standard to another, from one file sizeto another, etc.). VCMS 210 may also encrypt data and communicate withDRM server 214 to enforce digital rights. In some cases, VCMS 210 mayalso supply content with particular regional (e.g., location-based)variations.

According to implementations described herein, VCMS 210 may solicit andprocess content uploaded from content sources 140. For example, VCMS 210may receive credentials to authorize users and provide a user interface(e.g., a web-based interface) to allow users to register, categorize,and upload content. VCMS 210 may also interface with catalog server 222to provide private or public catalog entries for registered content andmay generate links (e.g., URLs, etc.) to enable viewing devices 120 toaccess registered content.

Content delivery system 212 may include one or more network devices, orother types of computation or communication devices, to delivermultimedia content from a backend server to user devices 270. In oneimplementation, content delivery system 212 may include a streamingserver that provides streaming data packets (e.g., via a streaming URL)to user devices 270 (e.g., via network 280). Content delivery system 212may provide content via different delivery mechanisms, such as abroadcast stream, a multicast stream, or a unicast stream, as determined(at least in part) by the type of content and the projected viewingaudience size. In one implementation, a streaming URL may besession-based, such that each URL can be used only once for one userdevice 270 for security purposes. In another implementation, contentdelivery system 212 may provide interactive content, such as games, etc.

DRM server 214 may include one or more network devices, or other typesof computation or communication devices, to issue, validate, and/orenforce DRM licenses to a client, such as an application running on oneof user devices 270. In implementations herein, DRM server 214 maycommunicate with user device 270 to authenticate a user of user device270, the particular user device 270, and/or an application residing onuser device 270. For example, DRM server 214 may request/receive logininformation associated with the user, and compare the login informationwith stored information to authenticate the user. Additionally, oralternatively, DRM server 214 may request/receive device information(e.g., a unique device identifier) associated with user device 270 andmay compare the device information with stored information toauthenticate user device 270.

Data center 220 may include one or more network devices, or other typesof computation or communication devices, to manage the authorization,selection, scheduling, and/or purchase of multimedia content by a userof user devices 270. As shown in FIG. 2, data center 220 may include acatalog server 222, an application server 224, and channel plans 226. Inone implementation, data center 220 may be accessed by user devices 270via access network 290.

Catalog server 222 may include one or more network devices, or othertypes of computation or communication devices, to provide a unifiedcatalog of multimedia content for users (e.g., of user devices 270) toconsume (e.g., view, buy, or rent). Catalog server 222 may include, forexample, program guide data for television content, on-demand contentdata, games, etc. In one implementation, catalog server 222 may collectand/or present listings of content available to user devices 270. Forexample, catalog server 222 may receive content metadata, such as listsor categories of content, from VCMS 210. Catalog server 222 may use thecontent metadata to provide currently-available content options to userdevices 270. In one implementation, private content (e.g., contentavailable to accounts/users identified by a content source) may beincluded in catalog listings provided to applicable users of navigationsdevices 110. Catalog server 222 may provide the content metadata to userdevices 270 directly or may communicate with user devices 270 viaapplication server 224.

Application server 224 may include one or more network devices, or othertypes of computation or communication devices (e.g., a server device, anapplication server device, a Web server device, a database serverdevice, a computer, etc.), to provide a backend support system formobile applications residing on user devices 270. For example,application server 224 may permit user devices 270 to download apersonal channel manager application that may permit a user to findcontent of interest, schedule content presentation, and/or playdownloaded or streaming content. The personal channel managerapplication may enable user devices 270 to present, to a user of userdevice 270, information received from data center 220 in an interactiveformat to allow selection of particular multimedia content.Additionally, or alternatively, application server 224 may providecontent metadata, such as lists or categories of content. Also,application server 224 may authenticate a user who desires to view,purchase, or rent multimedia content. In one implementation, theinteractions between application server 224 and user device 270 may beperformed using hypertext transfer protocol (HTTP) or secure HTTP(HTTPS) via access network 290.

Channel plans 226 may include a stored schedule of selected contentitems (e.g., selected by a user from catalog server 222) forpresentation. In one implementation, channel plans 226 may be associatedwith a single user (e.g., a personalized channel owner). In anotherimplementation, channel plans 226 may be associated with multiple users(e.g., a personalized channel owner and one or more followers) andmultiple user devices 270. In one aspect, data center 220 may monitorthe number of “followers” associated with a particular channel plan toidentify if multicast delivery methods (e.g., using mobile broadcastingmultimedia service (MBMS)) may be useful for content delivery ofnon-broadcast content. In another aspect, data center 220 may comparemultiple different channel plans to identify instances where the sameunicast content is scheduled for simultaneous distribution on differentpersonalized channels. If instances of simultaneous unicast distributionare identified, data center 220 may elect to apply multicast contentdelivery methods.

Profile server 230 may include one or more network devices, or othertypes of computation or communication devices, to store user profileinformation for users (e.g., users of user devices 270). Profile server230 may store per-user and/or per-device preferences. The user profileinformation may include various information regarding a user, such aslogin information (e.g., a user identifier and a password), billinginformation, address information, types of services to which the userhas subscribed, parental control settings, preferred display format,subtitle defaults, relevant advertising settings, most-watched media, alist of multimedia content purchased by the user, user deviceidentifiers (e.g., a media player identifier, a mobile deviceidentifier, a set top box identifier, a personal computer identifier,etc.) for user devices 270 associated with a user, user contentpreferences, user tendencies, or the like. In one implementation,profile server 230 may include and/or access a database that includesuser/device information from other systems, such as a wireless dataservice plan, a television subscription plan, or an Internet serviceplan. Thus, metadata from a single user on multiple devices (e.g.,mobile devices, television-based devices, computing devices, etc.) maycontribute to user profiles maintained by profile server 230.Application server 224 may use the user profile information from profileserver 230 to authenticate a user and may update the user profileinformation based on the user's activity (e.g., with a user's expresspermission).

Advertising server 240 may include one or more network devices, or othertypes of computation or communication devices, that store advertisingcontent that may be delivered to user devices 270. The advertisingcontent may include, for example, metadata that allows the advertisingcontent to be associated with particular groups, categories, and/orprofiles. The advertising content may include, for example, a uniqueidentifier for each particular advertisement. In one implementation,advertising server 240 may provide advertising content for insertioninto a content stream from VCMS 210.

Suggestion engine 250 may include one or more network devices, or othertypes of computation or communication devices, that provide suggestionsand/or recommendations of specific content (e.g., TV programming, VODtitles, video games, etc.) based on user profiles (from profile server230), user preferences (e.g., as indicated in a personal channel managerapplication), or other factors, such as popularity ratings for a show.In one implementation, suggestion engine 250 may provide a suggestionfor a scheduled time slot in a personal channel. Suggestion engine 250may also take into account subscription restrictions, pre-definedparameters set by parents, time-slot length, etc. In someimplementations, suggestion engine 250 may track user activity from atelevision subscription plan, a wireless data plan, and/or an Internetservice plan to learn user viewing habits and provide contentrecommendations.

Customer support system 260 may include one or more network devices, orother types of computation or communication devices, to solicit and/orreceive user feedback, questions, or credit-related requests. In oneimplementation customer support system 260 may include interfaces withdata center 220 and/or a billing system (not shown), for example, toreceive problem reports and to resolve customer billing disputes.

User devices 270 may generally include navigation devices 110, viewingdevices 120, and other computing devices. Navigation device 110 mayinclude a computation or communication device to enable a user toschedule presentation of content and/or interact with viewing device 120to cause presentation of content. Navigation device 110 may include, forexample, a personal communications system (PCS) terminal, a tabletcomputer, a smartphone, a personal computer, a laptop computer, awearable computer, or other types of computation or communicationdevices. In one implementation, navigation device 110 may include apersonal channel manager application that enables navigation device 110to communicate with, for example, data center 220 and/or presentinformation received from data center 220 to a user. The personalchannel manager application may permit a user of navigation device 110to log into an account (e.g., via application server 224), accesscatalog information (e.g., from catalog server 222), obtain contentlinks to scheduled content, and/or provide presentation instructions toviewing device 120.

Viewing device 120 may include a device that can present contentidentified by navigation device 110. Viewing device 120 may include, forexample, an STB (e.g., connected to a television), a gaming console, anInternet television, a smart television (e.g., a network-connectedtelevision), a computing device with a cable card, etc. Viewing device120 may execute a host application to communicate via a local wired orwireless connection with navigation device 110. In one implementation,viewing device 120 may execute an application to communicate via accessnetwork 290 with, for example, VCMS 210 or web server 295 to presentcontent based on instructions from navigation device 110. In anotherimplementation, viewing device 120 may be equipped with a dongle topermit secure communications with a personal channel manager applicationon navigation device 110. In some instances, navigation device 110 andviewing device 120 may be combined in a single device. In oneimplementation, viewing device 120 may be a closed device (e.g.,including a hardware/software configuration that is not accessible tothe general public), such as an STB with a unique identifier (e.g., aserial number) that can be used to associate a particular STB with aparticular customer/location.

Private network 280 may include, for example, one or more private IPnetworks that use a private IP address space. Private network 280 mayinclude a local area network (LAN), an intranet, a private wide areanetwork (WAN), etc. In one implementation, private network 280 mayimplement one or more Virtual Private Networks (VPNs) for providingcommunication between, for example, any of VCMS 210, data center 220,profile server 230, advertising server 240, suggestion engine 250,and/or customer support system 260. In one implementation, privatenetwork 280 may be protected/separated from other networks, such asaccess network 290, by a firewall. Although shown as a single element inFIG. 2, private network 280 may include a number of separate networks.

Access network 290 may include a local area network (LAN), a wide areanetwork (WAN), such as a cellular network, a satellite network, a fiberoptic network, a private WAN, or a combination of the Internet and aprivate WAN, etc., that is used to transport data. In oneimplementation, access network 290 may include a managed network thatcan be used to provide guaranteed service rates and QoS to user devices270. Although shown as a single element in FIG. 2, access network 290may include a number of separate networks that provide services to userdevices 270.

Web server 295 may include one or more network devices, or other typesof computation or communication devices, to receive provide informationto user devices 270 and/or to receive information from user devices 270.In one implementation, web server 295 may be part of a social mediaplatform to received and distribute files, such as a personalizedchannel plan, uploaded by a user of user device 270. In anotherimplementation, web server 295 may include an Internet content source, asearch engine, etc.

FIG. 3 is a diagram of exemplary components of a device 300. Each ofVCMS 210, content delivery system 212, DRM server 214, data center 220,catalog server 222, application server 224, profile server 230,advertising server 240, suggestion engine 250, customer support system260, user device 270, and web server 295 may be implemented/installed assoftware, hardware, or a combination of hardware and software, on one ormore of device 300. In one implementation, device 300 may be configuredas a network device. In another implementation, device 300 may beconfigured as a computing device. As shown in FIG. 3, device 300 mayinclude a bus 310, a processing unit 320, a memory 330, an input device340, an output device 350, and a communication interface 360.

Bus 310 may permit communication among the components of device 300.Processing unit 320 may include one or more processors ormicroprocessors that interpret and execute instructions. In otherimplementations, processing unit 320 may be implemented as or includeone or more application specific integrated circuits (ASICs), fieldprogrammable gate arrays (FPGAs), or the like.

Memory 330 may include a random access memory (RAM) or another type ofdynamic storage device that stores information and instructions forexecution by processing unit 320, a read only memory (ROM) or anothertype of static storage device that stores static information andinstructions for the processing unit 320, and/or some other type ofmagnetic or optical recording medium and its corresponding drive forstoring information and/or instructions.

Input device 340 may include a device that permits an operator to inputinformation to device 300, such as a keyboard, a touch screen, a keypad,a mouse, a pen, a microphone, one or more biometric mechanisms, a voiceor speech recognition system, and the like. Output device 350 mayinclude a device that outputs information to the operator, such as adisplay, a speaker, etc.

Communication interface 360 may include a transceiver that enablesdevice 300 to communicate with other devices and/or systems. Forexample, communication interface 360 may include wired or wireless(e.g., radio frequency) mechanisms for communicating with other devices,such as other devices of network 200.

As described herein, device 300 may perform certain operations inresponse to processing unit 320 executing software instructionscontained in a computer-readable medium, such as memory 330. Acomputer-readable medium may include a tangible, non-transitory memorydevice. A memory device may include space within a single physicalmemory device or spread across multiple physical memory devices. Thesoftware instructions may be read into memory 330 from anothercomputer-readable medium or from another device via communicationinterface 360. The software instructions contained in memory 330 maycause processing unit 320 to perform processes described herein.Alternatively, hardwired circuitry may be used in place of or incombination with software instructions to implement processes describedherein. Thus, implementations described herein are not limited to anyspecific combination of hardware circuitry and software.

Although FIG. 3 shows exemplary components of device 300, in otherimplementations, device 300 may include fewer components, differentcomponents, differently arranged components, or additional componentsthan depicted in FIG. 3. As an example, in some implementations, adisplay may not be included in device 300. In these situations, device300 may be a “headless” device that does not include an input device.Alternatively, or additionally, one or more components of device 300 mayperform one or more other tasks described as being performed by one ormore other components of device 300.

FIG. 4 is a block diagram of exemplary functional components ofnavigation device 110. The functions described in connections with FIG.4 may be performed by one or more components of device 300 (FIG. 3),such as processing unit 320 executing instructions stored in memory 330.As shown in FIG. 4, navigation device 110 may include a personal channelmanager application 400 that includes a channel setup module 410, aprofile configuration module 420, a viewing device interface 430, and achannel plan storage module 440. Generally, personal channel managerapplication 400 may allow a navigation device 110 solicit a personalizedcontent schedule from a user and to direct presentation of thepersonalized content schedule on viewing device 120.

Channel setup module 410 may provide a user interface to present contentoptions and configure a personalized content schedule (or channel plan).Content options may include, for example, items from catalog server 222,items from web server 295, and/or other multimedia content accessiblevia access network 290. In one implementation, channel setup module 410may provide a grid of time slots that can be selectively filled in withcontent items from a catalog listing. For example, channel setup module410 may include a drag-and-drop interface to insert content selectionsinto a particular time slot in the grid. In one implementation, selectedlinear content (e.g., television content, VOD content, downloads,streaming media, etc.) may automatically fill an amount of time in thegrid that corresponds to a selected program. In another implementation,selected non-linear content (e.g., games, music, social media, etc.) maybe assigned a duration by the user. In still another implementation, auser may assign a default channel or content source for any time periodnot otherwise scheduled in the personalized content schedule. Channelsetup module 410 may also be used to modify existing channel plans.Channel setup module 410 may communicate with content distributionnetwork 130 to obtain particular links (e.g., URLs) for content items inthe personalized content schedule. In some implementations, channelsetup module 410 may also provide new/updated channel plans to contentdistribution network.

Profile configuration module 420 may provide a user interface to solicituser preferences. For example, profile configuration module 420 mayallow a user to provide definitive settings to guide/limit suggestedcontent. Settings provided by a user may include, for example, user data(e.g., age, gender, etc.) and/or content preferences, such as contentratings (Motion Picture Association of America (MPAA) ratings, etc.),content age, favorite actors, preferred genres, minimum critic/viewerratings, etc. In one implementation, profile configuration module 420may communicate with profile server 230, advertising server 240, and/orsuggestion engine 250 to allow content distribution network 130 toidentify suggested content and/or advertising for a user's personalizedchannel.

Viewing device interface 430 may communicate with viewing device 120 topresent a personalized content schedule from channel setup module 410.In one implementation, viewing device interface 430 may communicate witha host application executed on viewing device 120 to instruct viewingdevice 120 when and what channel/content to display. For example,viewing device interface 430 may monitor the personalized contentschedule and, depending on the type of content included in the currenttime slot of a personalized content schedule (e.g., channel plan 115),viewing device interface 430 may instruct viewing device 120 to tune toa particular broadcast channel, load VOD content, or access a URL forweb-based content.

Viewing device interface 430 may monitor a personalized contentschedule, retrieve one or more links to upcoming content, and providethe links to viewing device 120 for presentation according to thepersonalized content schedule. Viewing device interface 430 may identifyviewing devices 120 that are available to present a personalized contentschedule based on instructions from navigation device 110. In oneimplementation, viewing device interface 430 may identify viewing device120 via wireless network discovery protocols, such as WiFi protocols,Bluetooth protocols, or other wireless protocols. In anotherimplementation, viewing device interface 430 may apply additionalapplication programming interfaces (APIs), protocols, and/or proceduresto identify a type of viewing device 120.

Channel plan storage module 440 may retrieve and/or store personalizedchannel plans. For example, channel plan storage 440 may store multiplepersonalized channel plans for a single user or for different users ofnavigation device 110. In one implementation, channel plan storagemodule 440 may also upload a personalized channel plan to contentdistribution network 130.

Although FIG. 4 shows exemplary functional components of navigationdevice 110, in other implementations, navigation device 110 may includefewer components, different components, or additional components thandepicted in FIG. 4. Alternatively, or additionally, one or morefunctional components of navigation device 110 may perform one or moreother tasks described as being performed by one or more other functionalcomponents of navigation device 110. Furthermore, one or more functionalcomponents of FIG. 4 may be performed on a different user device 270.For example, in some implementations, channel setup module 410 may beaccessed with user device 270 via a website account and the resultingpersonalized channel plan later retrieved/stored on navigation device110.

FIG. 5 is a diagram of exemplary functional components of VCMS 210. Inone implementation, the functions described in connection with FIG. 5may be performed by one or more components of device 300 (FIG. 3), suchas processing unit 320 executing instructions store in memory 330. Asshown in FIG. 5, VCMS 210 may include an uplink interface module 510, acatalog interface module 520, link creation module 530, andbuffer/storage module 540.

Uplink interface module 510 may provide an interface to enable users ofcontent source 140 to upload and register content for distributionthrough content distribution network 130. In one implementation, uplinkinterface module 510 may include a web server to provide a web page toallow a user to navigate through a content uploading process. In anotherimplementation, uplink interface module 510 may interact with a clientapplication at content source 140. Uplink interface module 510 may allowa user to designate content for publication as live (e.g., real-time) orstored (e.g., on-demand). Uplink interface module 510 may also allowcontent to be designated as public (e.g., generallyaccessible/searchable to those with access to content distributionnetwork 130) or private (e.g., restricting access to designatedusers/accounts). Other content settings configurable through uplinkinterface module 510 are described further in connection with theexemplary user interface of FIG. 9 below.

Catalog interface module 520 may obtain content descriptors and/ormetadata for uploaded content and provide the relevant contentdescriptors and/or metadata to catalog server 222. For example, cataloginterface module 520 may collect and store data received via uplinkinterface module 510 and generate a catalog entry with information suchas a title, source, and searchable keywords to be made available tousers of navigation devices 110.

Link creation module 530 may generate one or more unique links forcontent uploaded via uplink interface module 510. For example, linkcreation module 530 may generate a unique URL for uploaded content basedon a title, source, date, etc. In one implementation, link creationmodule 530 may apply a hash algorithm to generate the URL fromdesignated content metadata fields.

Buffer/storage module 540 may manage receipt and storage of uploadedcontent 540. In one implementation, buffer/storage module 540 mayperform a checksum or signature verification. Additionally, oralternatively, buffer/storage module 540 may use metadata from aparticular upload request via uplink interface module 510 to confirm allsegments for a particular content upload are received. Buffer/storagemodule 540 may also designate and track storage of uploaded content inone or more memory locations of content distribution network 130.

Although FIG. 5 shows exemplary functional components of VCMS 210, inother implementations, VCMS 210 may include fewer components, differentcomponents, or additional components than depicted in FIG. 5.Alternatively, or additionally, one or more functional components ofVCMS 210 may be performed by one or more other devices in contentdistribution network 130.

FIG. 6 is a diagram of exemplary functional components of contentdelivery system 212. In one implementation, the functions described inconnection with FIG. 6 may be performed by one or more components ofdevice 300 (FIG. 3), such as processing unit 320 executing instructionsstore in memory 330. As shown in FIG. 6, content delivery system 212 mayinclude a content server 610 and a multicast module 620.

Content server 610 may temporarily store and provide content requestedby navigation device 110 and/or viewing device 120. In oneimplementation, access to content server 610 (e.g., by navigation device110 and/or viewing device 120) may be restricted by a service providerthat operates VCMS 210. For example, access to content server 610 may berestricted to users with particular subscription packages and enforcedby, for example, password protection, device identifiers (for userdevices 270), and/or application identifiers (e.g., personal channelmanager application 400, etc.). Content server 610 may include otherdevices (not shown), such as a policy management server, a streamingdevice, a router, a content cache, etc. In some instances, contentserver 610 may provide a separate channel/link of the same content fordifferent content formats. For example, content server 610 may generatea content stream that is compatible with a platform (e.g., a particularcombination of hardware software) of some user devices 270, whileanother content stream (e.g., having a different data format and/orresolution) may be used for other types of user devices 270.

Multicast module 620 may identify if demand for content from a sharedpersonal channel should be included in a multicast stream. For example,when a large number of user devices 270 are following a particularpersonalized channel plan 115 (such as a celebrity's personalizedchannel with a large number of social media followers), contentdistribution network 130 may benefit from multicast delivery forparticular live or on-demand content scheduled in the personalizedchannel plan 115. Multicast module 620 may configure multicast sessionsfor distribution of the digital content. For example, multicast module620 may communicate with a multicast streaming device to streamrequested video content associated with a personal channel. Multicastmodule 620 may use internet protocol (IP) multicast addresses for IPflows that can be received simultaneously by viewing devices 120 (e.g.,viewing devices that are subscribed to and have joined a particularmulticast group associated with a content selection for the personalizedchannel).

In another implementation, multicast module 620 may utilize multicaststreaming in a manner that optimizes use of network and/or mediastreaming resources for delivery of on-demand content. For example,multicast module 620 may provide different unicast segments (e.g., tostart an on-demand program) and multicast segments (e.g., of anin-progress multicast delivery) to a viewing device 120. Multicastmodule 620 may work with viewing devices 120 to provide this hybrid ofunicast and multicast content simultaneously so that viewing devices 120may buffer multicast portions as needed to assemble and provide a linearpresentation.

Although FIG. 6 shows exemplary functional components of contentdelivery system 212, in other implementations, content delivery system212 may include fewer components, different components, or additionalcomponents than depicted in FIG. 6. Alternatively, or additionally, oneor more functional components of content delivery system 212 may beperformed by one or more other devices of network 200.

FIG. 7 is a diagram of exemplary functional components of applicationserver 224. In one implementation, the functions described in connectionwith FIG. 7 may be performed by one or more components of device 300(FIG. 3), such as processing unit 320 executing instructions store inmemory 330. As shown in FIG. 7, application server 224 may include adevice server module 710, a content aggregator module 720, asearch/suggestion module 730, and a selection module 740.

Device server module 710 supports interactions between user devices 270(e.g., navigation device 110 and/or viewing device 120) and backendservers, including (but not limited to) content delivery system 212, DRMserver 214, and catalog server 222. Device server module 710 maydetermine which content format to use according a device type orplatform of viewing device 120. For example, in one implementation,navigation device 110 may request, from application server 224, astreaming link or channel identifier for an item in a personalizedcontent schedule just prior to a scheduled time slot. The request mayinclude a content identifier and an identifier for viewing device 120.Device server module 710 may identify an appropriate format (e.g., bitrate, resolution, standard, file size, etc.) for the requested contenton viewing device 120.

Based on the selected content and format, device server module 710 mayprovide/generate a streaming link. Navigation device 110 may receive thestreaming link and provide the streaming link to viewing device 120 topresent the scheduled content. In another implementation, viewing device120 may request the streaming link for the item in the personalizedcontent schedule based on instructions from navigation device 110, anddevice server module 710 may provide the content link directly toviewing device 120. In one implementation, device server module 710 mayidentify a location of viewing device 120 (e.g., based on accountinformation and a device identifier) and provide/generate a streaminglink based on the location (along with the content selection and devicetype). For example, a location may be used to select a link withparticular advertising, regional content, and/or blackouts.

Content aggregator module 720 aggregates information from Internetsearching and social networks related to particular content (e.g., aprogram or video) for a user to include in a personalized channel. Inone implementation, content aggregator module 720 may provide links orother menu options to enable a user to schedule content provided bycontent aggregator module 720.

Search/suggestion module 730 enables users to search catalog server 222and other devices/systems by keywords, titles, sources, etc.Search/suggestion module 730 may also provide ranked search resultsbased on the user's search terms, profile, viewing history, orpreviously-purchased content. In one implementation, search/suggestionmodule 730 can also automatically recommend particular content to theuser based on input from suggestion engine 250.

Selection module 740 enables users to review and select content from avariety of sources, including items from catalog server 222 and contentaggregator module 720. Selection module 740 may support browsing andsearching of a customized content list (e.g., a unified catalog fromcatalog server 222 and content aggregator module 720) from navigationdevice 110/personal channel manager application 400. In oneimplementation, selection module 740 may include a customized contentlisting based on a user's subscription package with a service provider(e.g., a basic, extended, or premium service option). In anotherimplementation, selection module 740 may include, in a customizedcontent listing, other personalized channels from a user's social mediacontacts. In some implementations, selection module 740 may also providean electronic shopping cart, transaction management, and/or promotionsand advertisements.

Although FIG. 7 shows exemplary functional components of applicationserver 224, in other implementations, application server 224 may includefewer components, different components, or additional components thandepicted in FIG. 7. Alternatively, or additionally, one or morefunctional components of application server 224 may be performed by oneor more other devices of content distribution network 130.

FIG. 8 is a diagram of exemplary communications for a portion 800 ofnetwork 200. Communications in FIG. 8 may represent communications toconfigure, and view content from, a personalized channel according toimplementations described herein. As shown in FIG. 8, network portion800 may include navigation device 110, viewing device 120, contentsource 140, VCMS 210, and data center 220. Navigation device 110,viewing device 120, content source 140, VCMS 210, and data center 220may include features described above in connection with, for example,FIGS. 1-7.

As shown in FIG. 8, content source 140 may upload content 810 andassociated content metadata 815 to VCMS 210. In one implementation, VCMS210 (e.g., uplink interface module 510) may provide a graphical userinterface to solicit content 810 and content metadata 815. In oneimplementation, content 810 and metadata 815 may be providedconcurrently. For example, if content 810 is previously recordedcontent, a user at content source may provide a complete content fileand metadata. In another implementation, metadata 815 may be providedbefore content 810, such as when content 810 is live linear contentscheduled for a future time. FIG. 9 provides a schematic of an exemplaryuser interface 900 that may be used to guide the uploading of content810 and metadata 815.

Referring to FIG. 9, user interface 900 may be presented, for example,on a computing device, such as a user device 270 or another computingdevice. In one implementation, user interface 900 may be included aspart of content upload client application. In another implementation,user interface 900 may be included in a web page accessible through abrowser application.

As shown in FIG. 9, user interface 900 may include a content sourcesection 910, an access control section 920, a description section 930,and a link section 940. Content source section 910 may include separatetabs 912 and 914 (or subsections) for live content and recorded content,respectively. Live content tab 912 may solicit information relevant touploading of linear content for real-time (or near-real-time)presentation. Thus, live content tab 912 may include an input sourcesection 916 to identify a source (such as an internal camera of acomputing device or an external device connected via a wired or wirelessport) for a live media stream. Live content tab 912 may also include atitle section 917, a schedule section 918, and an options section 919.Title section 917 may include an input section to receive a name for thecontent/program to be uploaded. Schedule section 918 may solicit a date,start time, and end time for the live content. In one implementation,schedule section 918 may require only a start time and identify an endtime when signaled by, for example, the content upload clientapplication at content source 140. Options section 919 may allow theuser to identify parameters for the live content feed, such a connectionspeed, video format, additional source information, etc.

Recorded content tab 914 may be selected by the user to upload, forexample, a content file. Recorded content tab 914 may solicit, forexample, a file name and local storage location for the content file.

Content attributes from access control section 920, description section930, and link section 940 may be applied to content uploads from eitherof live content tab 912 or recorded content tab 914 in content sourcesection 910. Access control section 920 may allow a user to identifycontent as either private or public. Private content may be limited toparticular viewer or groups of viewers. For example, private content maybe restricted by the user that uploads/produces the content to permitaccess by only particular users (e.g., user accounts) or to any contactin the user's contact list. In one implementation, access controlsection 920 may automatically notify a list of contacts when contentfrom the user is published. Public content may be viewed by, forexample, any user of content distribution network 130.

Description section 930 may include an entry form to allow a user toinput keywords and/or tags to be associated as metadata (e.g., metadata815) with the particular uploaded content. In one implementation,description section 930 may provide keyword suggestions (e.g., based onprevious entries, current trends, etc.). In another implementation,textual descriptions may be used (e.g., up to a limited amount ofcharacters).

Link section 940 may include a prompt to cause VCMS 210 to generate alink (e.g., a dedicated identifier or URL) for the particular content.The link may be associated with the content and identify a networklocation (e.g., in content distribution network 130) through which theuploaded content can be accessed. The link may be provided to contacts,for example, to access the content without relying on catalog server 222and may be shared over social media.

Although FIG. 9 depicts certain user interfaces for configuring apersonalized channel, in other implementations, different userinterfaces may be used that depict more, less, and/or differentinformation than depicted in FIG. 9.

Returning to FIG. 8, VCMS 210 may receive uploaded (e.g., live orrecorded) content 810 and metadata 815 from content source 140. VCMS 210may compile data from content 810 and metadata 815 into catalog data820. VCMS 210 may forward catalog data 820 to data center 220 (e.g., fordistribution by catalog server 222). Navigation device 110 may retrievecontent list 825 from data center 220. The content list 825 may include,for example, content items from catalog server 222 that are responsiveto a particular search query from navigation device 110. For example,the one of the responsive content items may include content 810.Navigation device 110 (e.g., using personal channel manager application400) may solicit user input to incorporate desired content items (suchas content item 810) from content list 825 into a selection 830.Selection 830 may include, for example, a single content item selectionand a viewing device identifier. Alternatively, selection 830 may beincluded within a personalized channel plan. In another implementation,navigation device 110 may receive a notification of particular content(e.g., private content) via a notification message (not shown) andincorporate, into selection 830, a link for the content listing incatalog server 222.

In response to selection 830, data center 220 may provide a content link835, such as a URL or channel identifier, to navigation device 110 toenable viewing device 120 to tune to or view the content selected by theuser. In one implementation, content links 835 may include a URL for aprivate managed network (e.g., a private portion of access network 290).Thus, if accessible to viewing device 120, a service provider mayprovide requested content with guaranteed QoS levels and/or otherbenefits that may not be available through a public network or withnon-Guaranteed Bit Rate (GBR) traffic. For example, one or more ofcontent links 835 may direct a device (e.g., viewing device 120) to anetwork location that is only accessible to particular devices (e.g., aproprietary STB) or particular accounts (e.g., subscribers with verifiedaccount credentials). In other implementations, one or more of contentlinks 835 may provide unrestricted access to content.

Navigation device 110 may receive content link 835 and may providecontent link 835 to viewing device 120 for presentation of the content.Content link 835 may include, for example, the network location forviewing device 120 to obtain the required content feed from VCMS 210.

Viewing device 120 may use content link 835 to retrieve content fromVCMS 210. In some implementations, content may require DRMauthentication via DRM server 214.

For example, content associated with selection 830 may be subject tocopyright and/or license restrictions. Viewing device 120 may access astreaming URL (e.g., via content link 835) to request the particularcontent from VCMS 210. In response, VCMS 210 (e.g., content deliverysystem 212) may begin streaming the requested channel content 850,including a content header. A content header can include informationabout where to fetch a DRM license to permit viewing device 120 todisplay the channel content 850. Based on the content header, viewingdevice 120 may submit a separate license request to VCMS 210 (e.g., DRMserver 214) to retrieve a DRM license before presenting the content.

In another implementation, VCMS 210 may also apply information fromprofile server 230 and/or advertising server 240 to provide targetedadvertising to the user providing selection 830.

Although FIG. 8 shows exemplary communications within network portion800, in other implementations, different communications may be used thandepicted in FIG. 8. For example, in another implementation, content link835 may include a channel identifier that can be tuned to by viewingdevice 120 (e.g., when viewing device 120 includes a STB/TVcombination).

FIG. 10 is a flow diagram of an exemplary process 1000 for publishingcontent for access via a personalized channel. In one implementation,process 1000 may be performed by one or more devices in contentdistribution network 130. In other implementations, process 1000 may beperformed by navigation device 110 and/or viewing device 120 inconjunction with one or more devices from content distribution network130.

Process 1000 may include receiving and authenticating login credentialsfor a content source (block 1010) and providing an uplink user interfaceto describe and upload video content (block 1020). For example, VCMS 210may receive an account user name and password for a subscriber ofcontent sharing services. VCMS 210 may verify the user name and passwordto provide access, for example, to a web page with an uplink userinterface (e.g., user interface 900) that allows the user to describeand upload content.

Process 1000 may also include receiving descriptive information for thevideo content via the uplink user interface (block 1030) and generatinga unique content identifier for the video content (block 1040). Forexample, using the uplink user interface (e.g., user interface 900), auser at content source 140 may identify content as live or recordedvideo content, provide a title, identify a source, provide accessrestrictions (e.g., public/private access), and provide contentdescriptors. VCMS 210 may receive the user input and may assign acontent identifier. If the content is live content, VCMS 210 may providethe content identifier in advance of receiving uploaded content. If thecontent is recorded content, VCMS 210 may provide the content identifierin advance, concurrently, or after receiving the uploaded content. Theunique content identifier may be used, for example, in a link and/ornotification message to potential viewers (e.g., for private content)and/or in a catalog of content.

Process 1000 may further include incorporating the listing of the videocontent into a catalog of content available to users (block 1050). Forexample, VCMS 210 may communicate with data center 220 (e.g., catalogserver 222) to provide catalog updates that include content uploads (orscheduled uploads for live linear content) from content source 140.Users of navigation device 110 may identity content from content source140 via title searches, keyword searches, source searches, or categorysearches of a catalog listing (from catalog server 222) based on, forexample, various metadata previously provided via user interface 900.

Process 1000 may additionally include receiving the video content fromthe content source (block 1060), receiving a request, from a userdevice, to view the video content (block 1070), and providing a link toview the video content via the content distribution network (block1080). For example, as described in connection with FIG. 8, contentsource 140 may provide video content (e.g., content 810) to VCMS 210.Based on a selection (e.g., using a unique content identifier from acatalog listing or a notification message for private access), anavigation device 110 may request a content link for the selectedcontent. Data center 220 may provide a content link (content link 835)to navigation device 110 to enable navigation device 110 to instruct aviewing device (e.g., viewing device 120) to retrieve and present theselected content.

Systems and/or methods described herein provide techniques formicro-publishers and other content providers to upload live andpreviously-recorded content for distribution as part of a contentaggregation platform. Network devices may provide, to a content sourcedevice, an uplink user interface to facilitate describing and uploadingof video content. The network devices may receive, via the uplink userinterface, descriptive information for the video content and generate,based on the descriptive information received via the uplink userinterface, a unique content identifier for the video content. Thenetwork devices may incorporate, based on the uploading, a listing ofthe video content into a catalog of content available to users of acontent distribution network. The network devices may receive, from thecontent source device, the video content and may receive, from a userdevice, a request to view the video content that includes the uniquecontent identifier. The network devices may provide, to the user device,a link to enable the user device to access the video content via thecontent distribution network.

In the preceding specification, various preferred embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded inan illustrative rather than restrictive sense. For example, while seriesof blocks have been described with respect to FIG. 10, the order of theblocks may be modified in other implementations. Further, non-dependentblocks may be performed in parallel.

It will be apparent that different aspects of the description providedabove may be implemented in many different forms of software, firmware,and hardware in the implementations illustrated in the figures. Theactual software code or specialized control hardware used to implementthese aspects is not limiting of the invention. Thus, the operation andbehavior of these aspects were described without reference to thespecific software code—it being understood that software and controlhardware can be designed to implement these aspects based on thedescription herein.

Further, certain portions of the invention may be implemented as a“component” or “system” that performs one or more functions. Thesecomponents/systems may include hardware, such as a processor, an ASIC,or a FPGA, or a combination of hardware and software.

To the extent the aforementioned embodiments collect, store or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Additionally, thecollection, storage and use of such information may be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as may be appropriate for thesituation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

No element, act, or instruction used in the present application shouldbe construed as critical or essential to the invention unless explicitlydescribed as such. Also, as used herein, the article “a” and “one of isintended to include one or more items. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise.

1. A method comprising: providing, by a network device and to a contentsource device, an uplink user interface to describe and upload videocontent; receiving, by the network device and via the uplink userinterface, descriptive information for the video content; generating, bythe network device and based on the descriptive information received viathe uplink user interface, a unique content identifier for the videocontent; incorporating, by the network device and based on thedescriptive information, a listing of the video content into a catalogof content available to users of a controlled access network thatprovides guaranteed quality of service (QoS) levels to subscribingviewers; receiving, by the network device and from the content sourcedevice, the video content; receiving, by the network device and from auser device, a request to view the video content, wherein the requestincludes the unique content identifier; and providing, by the networkdevice and to the user device, a link to enable a viewing device toaccess the video content via the controlled access network, wherein thelink is provided via a public access network that is different than thecontrolled access network.
 2. The method of claim 1, wherein the linkincludes a uniform resource locator (URL) or channel identifier for thecontrolled access network.
 3. The method of claim 1, wherein thecontrolled access network includes at least one of a closed cable or afiber-optic distribution network.
 4. The method of claim 1, furthercomprising: receiving, by the network device, login credentials for thecontent source device, wherein the login credentials identify anauthorized subscriber for content publishing services.
 5. The method ofclaim 1, wherein the link includes a uniform resource locator (URL)identifying a network location to retrieve content formatted for a typeof the user device.
 6. The method of claim 1, wherein the uplink userinterface solicits, from a user, a title for the video content, a sourcefor the video content, and descriptors for the video content.
 7. Themethod of claim 6, wherein the uplink user interface further solicitsthe user to provide a private access designation or a public accessdesignation for the video content.
 8. The method of claim 7, furthercomprising: limiting access to the listing to subscribers identified bythe user when the user provides a private access designation.
 9. Themethod of claim 1, wherein the video content includes live linearcontent.
 10. The method of claim 1, wherein the uplink user interfaceincludes one of a web page or an application for a mobile device. 11.The method of claim 1, wherein the viewing device is different than theuser device and wherein the link is further provided to the user devicevia a mobile access network.
 12. One or more network devices,comprising: a first network interface to communicate with a contentsource device; a second network interface to communicate with a userdevice that is different than the content source device; a memory forstoring instructions; and one or more processors to execute theinstructions to: provide, to a content source device via the firstnetwork interface, an uplink user interface to describe and upload videocontent; receive, via the uplink user interface, descriptive informationfor the video content; generate, based on the descriptive informationreceived via the uplink user interface, a unique content identifier forthe video content; incorporate, based on the descriptive information, alisting of the video content into a catalog of content available tousers of a controlled access network that provides guaranteed quality ofservice (QoS) levels to subscribing viewers; receive, from the contentsource device and via the first network interface, the video content;receive, from a user device, a request to view the video content,wherein the request includes the unique content identifier; and provide,to the user device via the second network interface, a link to enable aviewing device to access the video content via the controlled accessnetwork, wherein the link is provided via a public access network thatis different than the controlled access network.
 13. The one or morenetwork devices of claim 12, wherein the link includes a uniformresource locator (URL) or channel identifier for the controlled accessnetwork.
 14. The one or more network devices of claim 12, wherein theone or more processors are further to: deliver the video content usingunicast and multicast delivery of different portions of the videocontent.
 15. The one or more network devices of claim 12, wherein theuplink user interface solicits, from a user, descriptors for the videocontent, and wherein the one or more processors are further configuredto: associate the descriptors as metadata for the video content tofacilitate searches for the video content.
 16. The one or more networkdevices of claim 12, wherein the uplink user interface solicits, from auser, access designations for the video content, and wherein the one ormore processors are further to: limit access to the listing tosubscribers identified by the user when the user provides a privateaccess designation.
 17. The one or more network devices of claim 12,wherein the video content includes live linear video content.
 18. Anon-transitory computer-readable medium, storing instructions executableby one or more processors, the non-transitory computer-readable mediumcomprising one or more instructions to: provide, to a content sourcedevice via a first network interface, an uplink user interface todescribe and upload video content; receive, via the uplink userinterface, descriptive information for the video content; generate,based on information received via the uplink user interface, a uniquecontent identifier for the video content; incorporate, based on thedescriptive information, a listing of the video content into a catalogof content available to users of a controlled access network thatprovides guaranteed quality of service (QoS) levels to subscribingviewers; receive, from the content source device, the video content;receive, from a user device, a request to view the video content,wherein the request includes the unique content identifier; and provide,to the user device via a second network interface, a link to enable aviewing device to access the video content via the controlled accessnetwork, wherein the link is provided via a public access network thatis different than the controlled access network.
 19. The non-transitorycomputer-readable medium of claim 18, wherein the viewing device isdifferent than the user device and wherein the link is further providedto the user device via a mobile access network.
 20. The non-transitorycomputer-readable medium of claim 18, further comprising one or moreinstructions to: provide the video content to one or more subscriberdevices using multicast delivery.